home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: Destroying Proxy Frames
- Sent: 7/8/96 1:23 PM
- Received: 7/8/96 1:41 PM
- From: Henri Lamiraux, lamiraux@apple.com
- Reply-To: ODF Interest, ODF-Interest@CILabs.ORG
- To: OpenDoc Development Framework Discussion List, ODF-Interest@CILabs.
-
- >When a FW_CProxyFrame is destroyed should its fEmbeddedFrame be removed
- >or should it be released if that frame has been detached (fAttached =
- >FALSE)? Currently my part crashes when the fEmbeddedFrame has been
- >detached and is removed in CProxyFrame's destructor...
- >
-
- The answer to this question is a little bit complex. There are several
- problems in OpenDoc which make the whole Release vs Remove issue very
- complex to implement. ODF 1 tried to implement the OpenDoc recipes the
- best it could at the time. Since then many problems with InLimbo have
- been discovered in OpenDoc. ODF 2 implements a 'new and improved recipes'
- which should work much better.
-
- The value of fAttached is not enough to decide if you need to call
- release or remove. An embedded frame can be detached but being embedded
- in another frame (because you did a cut and paste or a drag/move).
- Calling remove by just testing fAttached is not enough, you might delete
- a frame embedded in another frame.
-
- What's concerning me about your fix is that if fAttached is true then
- inLimbo should be false (an attached embedded frame is not inLimbo). This
- means that you never execute the first if statement and never remove
- unused embedded frames.
-
-
- How do you detach embedded frames? is it the result of an undoable action
- (like cut or drag/move)?
-
- ........................................................................
- Henri Lamiraux lamiraux@apple.com
- Apple Computer, Inc. OpenDoc(tm) Development Framework
- ........................................................................
-
-
-